Handle 200 OK errors in PutObject (multipart) in S3 CRT client

Motivation and Context

Fixes: #7068

The CRT client already detects 200ok errors during MPU in PutObject, however, they are not correctly handled in our Java code.

The reason the normal handling of 200OK errors does not work for this case is that the 200OK error handling is normally only applied for non-streaming operations. PutObject is a streaming operation, but under the hood, the CRT may do a MPU, and complete multipart upload is not streaming and may respond with a 200 OK error.

Modifications

Wrap the SDK response object in a new ErrorFlaggedSdkHttpResponse which returns false for isSuccessful, causing the SDK's normal error parsing to be used.

Note, earlier PR #7071 does correctly raise an exception, but does not parse the code/message from the body. To avoid brining in xml parsing to the CRT handler, this PR wraps the sdk response object and relies on the existing error unmarshalling pipeline.

Testing

New and existing unit tests + ran repro from #7068 to confirm.

Screenshots (if appropriate)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

Checklist

• I have read the CONTRIBUTING document
• Local run of mvn install succeeds
• My code follows the code style of this project
• [] My change requires a change to the Javadoc documentation
• I have updated the Javadoc documentation accordingly
• I have added tests to cover my changes
• All new and existing tests passed
• I have added a changelog entry. Adding a new entry must be accomplished by running the scripts/new-change script and following the instructions. Commit the new file created by the script in .changes/next-release with your changes.

License

• I confirm that this pull request can be released under the Apache 2 license